-
Notifications
You must be signed in to change notification settings - Fork 65
📖 Improve formatting on the docs website #1446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
** Disable CRD Upgrade Safety Check:** | ||
**Command Example:** | ||
|
||
**Patch the ClusterExtension Resource:** | ||
If you prefer using the command line, you can use `kubectl` to modify the upgrade CRD safety check configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1446 +/- ##
=======================================
Coverage 74.91% 74.91%
=======================================
Files 42 42
Lines 3241 3241
=======================================
Hits 2428 2428
Misses 642 642
Partials 171 171
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
> [!NOTE] | ||
> Currently, OLM 1.0 does not support automatic upgrades to the next major version. You must manually verify and perform major version upgrades. For more information about major version upgrades, see [Manually verified upgrades and downgrades](#manually-verified-upgrades-and-downgrades). | ||
!!! note | ||
Currently, OLM 1.0 does not support automatic upgrades to the next major version. You must manually verify and perform major version upgrades. For more information about major version upgrades, see [Manually verified upgrades and downgrades](#manually-verified-upgrades-and-downgrades). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!!! note
This renders well in our mkdocs website, but not on GitHub. [!NOTE]
renders well on GitHub, but not in mkdocs.
Same applies to other admonitions.
We are changing these admonitions in docs
dir because these are docs which will be rendered on the website. Leaving everything outside of docs dir as is - these will likely be viewed via GitHub UI.
kind create cluster operator-controller | ||
``` | ||
```sh | ||
kind create cluster operator-controller |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was rendering fine in GH UI. However this doc is also used in the website. This formatting works fine in both GH and on the website.
77c1ae7
to
859f2ba
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming that you finished (since I cannot see in the title WIP)
Hi @m1kola
The emoji here is 📖 not 🌱
🌱 is only for things that does not bring impacted to the end users at all (i.e changes in the e2e tests)
So could you please fix the emoji?
Otherwise,
I gave a look on this one with the preview and all shows fine 🥇
Great work !!! Well done
/lgtm
Forgot we have a separate emoji for docs. Updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Requesting a few small changes
859f2ba
to
9f7db18
Compare
@trgeiger lovely stuff! Please take a look at the latest push: it addresses your feedback + I noticed a broken list under "Putting it all together" in |
@trgeiger: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/lgtm |
/lgtm |
@michaelryanpeter: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/lgtm |
9f7db18
to
118b870
Compare
Had to rebase due to #1228 |
Blocked by #1451. Will require another rebase once it merges. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
Fixes a number of formatting/rendering issues. Mostly around lists, admonitions (notes, warnings, etc) and collapsible text. Signed-off-by: Mikalai Radchuk <[email protected]>
118b870
to
c916dc7
Compare
New changes are detected. LGTM label has been removed. |
Rebased on top of #1451 so it can pass |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome! Thank you!!!
Description
Fixes a number of formatting/rendering issues. Mostly around lists, admonitions (notes, warnings, etc) and collapsible text.
Tip
Recommend reviewing the changes with

git diff --ignore-all-space
(-w
) option. GitHub UI also has this option.Tip
We also have docs deployment preview. See the comment from netlify bot below.
Reviewer Checklist